Systems and methods for providing an object platform for a relational database

ABSTRACT

Systems and methods are provided for providing an object platform for datasets A definition of an object may be obtained. The object may be associated with information stored in one or more datasets. The information may be determined based at least in part on the definition of the object. The object may be stored in a cache such that the information associated with the object is also stored in the cache. One or more interfaces through which requests to perform one or more operations on the object are able to be submitted may be provided.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. § 119(e) of U.S.Provisional Application Ser. No. 62/529,818, filed Jul. 7, 2017, thecontent of which is incorporated by reference in its entirety into thepresent disclosure.

FIELD OF THE INVENTION

This disclosure relates to approaches for providing an object platformfor datasets.

BACKGROUND

Under conventional approaches, data stored in relational databases maybe retrieved for presentation and/or operation. However, conventionalrelational databases may not support object-based operations.

SUMMARY

Various embodiments of the present disclosure may include systems,methods, and non-transitory computer readable media configured toprovide an object platform for datasets. A definition of an object maybe obtained. The object may be associated with information stored in oneor more datasets. The dataset(s) may be stored in one or more databases,such as a relational database. The information may be determined basedat least in part on the definition of the object. The object may bestored in a cache such that the information associated with the objectis also stored in the cache. One or more interfaces through whichrequests to perform one or more operations on the object are able to besubmitted may be provided.

In some embodiments, the definition of the object may be included withinan ontology. The ontology may define other aspects of the object, suchas how the properties of the object may be presented and/or modified.

In some embodiments, the operations may include searching for theobject, loading the object, or modifying the object.

In some embodiments, the object may be stored in an object store. Theobject may be modified within the cache and the modified object may bestored in the object store.

In some embodiments, the information in the dataset(s) may be changed.The information stored in the cache may be updated based on changes tothe information in the dataset(s).

In some embodiments, a change to the definition of the object (e.g.,within the ontology) may be identified. The object in the cache may beupdated based on the change to the definition of the object.

In some embodiments, information about modifications to the object maybe stored in a commit log. The information may include time stamps andvector clocks associated with the modifications to the object. Theinformation may identify the user/system that prompted/made themodifications. The information may identify the security level of theuser/system that prompted/made the modifications. The information mayidentify the priority level of the modifications.

In some embodiments, conflicts in the modifications to the object may beidentified based on the commit log. The conflicts may be resolved basedon one or more rules. The rule(s) may be set or configurable.

These and other features of the systems, methods, and non-transitorycomputer readable media disclosed herein, as well as the methods ofoperation and functions of the related elements of structure and thecombination of parts and economies of manufacture, will become moreapparent upon consideration of the following description and theappended claims with reference to the accompanying drawings, all ofwhich form a part of this specification, wherein like reference numeralsdesignate corresponding parts in the various figures. It is to beexpressly understood, however, that the drawings are for purposes ofillustration and description only and are not intended as a definitionof the limits of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain features of various embodiments of the present technology areset forth with particularity in the appended claims. A betterunderstanding of the features and advantages of the technology will beobtained by reference to the following detailed description that setsforth illustrative embodiments, in which the principles of the inventionare utilized, and the accompanying drawings of which:

FIG. 1 illustrates an example environment for providing an objectplatform for datasets, in accordance with various embodiments.

FIG. 2 illustrates an example environment for providing an objectplatform for datasets, in accordance with various embodiments.

FIG. 3 illustrates an example operation flow for using an objectplatform for datasets, in accordance with various embodiments.

FIG. 4 illustrates a flowchart of an example method, in accordance withvarious embodiments.

FIG. 5 illustrates a block diagram of an example computer system inwhich any of the embodiments described herein may be implemented.

DETAILED DESCRIPTION

A claimed solution rooted in computer technology overcomes problemsspecifically arising in the realm of computer technology. In variousimplementations, a computing system may obtain a definition of anobject. The object may be associated with information stored in one ormore datasets. The dataset(s) may be stored in one or more databases,such as a relational database. The information may be determined basedat least in part of the definition of the object. The object may bestored in a cache such that the information associated with the objectis stored in the cache. For example, the object may be associated with aset of values in one or more tables and these values may be stored inthe cache as properties of the object. The information stored in thecache may be updated based on changes to the information in thedataset(s). Storing the object in the cache may enable operations on theobject, such as searching, loading, and modifying the object. Suchoperations may be performed based on requests received through APIs(e.g., object search API, object load API, object modify API). Theobject may be found within the cache based on a search request. Theobject may be loaded based on a load request. The object may be modifiedbased on a modification request. For example, one or more properties ofthe object may be modified (e.g., added, removed, changed) and/or one ormore links may be created/removed/changed between the object and otherobjects. The object may be stored within an object store. The object maybe modified within the cache and stored within the object store. Thedataset(s) may be updated based on the modifications to the object inthe cache.

In some embodiments, the definition of the object may be included withinan ontology. The ontology may define other aspects of the object, suchas how the properties of the object may be presented and/or modified. Achange to the definition of the object (e.g., within the ontology) maybe identified. The object in the cache may be updated based on thechange to the definition of the object.

In some embodiments, information about modifications to the object maybe stored in a commit log. The information may include time stamps andvector clocks associated with the modifications to the object. Theinformation may identify the user/system that prompted/made themodifications. The information may identify the security level of theuser/system that prompted/made the modifications. The information mayidentify the priority level of the modifications. A conflict inmodifications to the object may be identified based on the commit log.The conflict may be resolved based on one or more rules. The rule(s) maybe set or configurable.

The approach disclosed herein enables usage (e.g. creating, viewing,modifying) of information stored in a database via object-oriented frontend. The approach disclosed herein provides a tool/service that supportsobject operations (e.g., searching, loading, modifying) on top of adatabase. Information associated with an object may be loaded into acache (e.g., as properties of the object). Loading theobject/information associated with the object into the cache may enableobject-oriented operations on the object/information associated with theobject. For example, particular information stored in a database mayrepresent properties of tangible/intangible things. By loading theparticular information representing the properties of the things into acache, users may interact with the particular information in terms ofthings. Loading the particular information into the cache may enableusers to operate on the particular information without loading theentirety of datasets and parsing the datasets for operations. Loadingthe particular information into the cache may enable to users to operateon the particular information using operations that are not supported bythe database. In general, the approaches described herein may be adaptedto provide an object platform for any dataset(s). Such dataset(s) may bestored (or ingested) in one or more databases. Many variations arepossible.

FIG. 1 illustrates an example environment 100 for providing an objectplatform for datasets, in accordance with various embodiments. Theexample environment 100 may include a computing system 102. Thecomputing system 102 may include one or more processors and memory. Theprocessor(s) may be configured to perform various operations byinterpreting machine-readable instructions stored in the memory. Theenvironment 100 may also include one or more datastores that areaccessible to the computing system 102 (e.g., via one or morenetwork(s)). In some embodiments, the datastore(s) may include variousdatasets, databases, application functionalities, application/datapackages, and/or other data that are available for download,installation, and/or execution.

In various embodiments, the computing system 102 may include a datastore112, a definition engine 114, an association engine 116, a cache engine118, and an interface engine 120. The datastore 112 may includestructured and/or unstructured sets of data that can bedivided/extracted for provisioning when needed by one or more componentsof the environment 100. The datastore 112 may include one or moredatasets of information. The dataset(s) may be stored in one or moredatabases, such as a relational database. A relational database mayorganize information/data into tables, columns, rows, and/or otherorganizational groupings. Groupings of information may belinked/referenced via use of keys (e.g., primary and foreign keys).While the computing system 102 is shown in FIG. 1 as a single entity,this is merely for ease of reference and is not meant to be limiting.One or more components/functionalities of the computing system 100described herein may be implemented in a single computing device ormultiple computing devices.

The definition engine 114 may be configured to obtain one or moredefinitions for one or more objects. Obtaining definition(s) may includeone or more of accessing, acquiring, analyzing, determining, examining,generating, locating, receiving, retrieving, reviewing, storing, and/orotherwise obtaining the definition(s). Definition(s) (previouslystored/created) may be obtained from one or more storage locations. Astorage location may refer to electronic storage located within thecomputing system 102 (e.g., integral and/or removable memory of thecomputing system 102), electronic storage coupled to the computingsystem 102, and/or electronic storage located remotely from thecomputing system 102 (e.g., electronic storage accessible to thecomputing system 102 through a network). Definition(s) may be obtainedfrom one or more user input (e.g., from a user's interaction with one ormore interfaces allowing the user to define an object). For example,definition(s) may be created/modified based on user input.

An object may refer to a thing/a grouping of things with a given set ofproperties. An object may reference tangible/intangible thing(s) and/oranimate/inanimate thing(s). As non-limiting examples, an object mayrefer to person(s), vehicle(s), portion(s) of a vehicle, building(s),portion(s) of a building, investigation(s), a portion(s) of aninvestigation, schedule(s), or right(s)/demands for right(s), and/orother things. Other types of objects are contemplated.

A definition of an object may describe the object byspecifying/identifying one or more properties (e.g., characteristics) ofthe object. For example, an object may include a person and a definitionof the object may describe the person by specifying/identifyingparticular properties (e.g., gender, height, weight, education,occupation, address, phone number) of the person. The values of theproperties of the object may be stored in a dataset(s) (e.g., ofrelational databases(s)). For example, the values of the properties maybe stored in one or more columns and/or rows of a database as strings,numbers, and/or other forms of expression. The definition of the objectmay identify the particular column(s) and/or row(s) of the databasestoring the relevant values of the properties of the object. In someembodiments, a given property of an object may be derived from one ormore values of dataset(s). For example, a given property of an objectmay be determined based on multiple values within one or more tables.

In some embodiments, an object may be related to one or more otherobjects. Relationship among objects may be between objects of same type(e.g., relationship between people objects, such as between familymembers, co-workers, persons who have interacted with each other) and/orbetween objects of different types (e.g., relationship between a personobject and a non-person object, such as between a person and a schedule,a person and an investigation). For example, objects representingindividual investigations (e.g., of accidents, of claims, of demands forrights) may be related to an object representing a group ofinvestigations (e.g., based on commonalities, based on user input). Suchrelationships may effectuate grouping individual investigations intogroups of investigations. As another example, objects representingindividual investigations (e.g., of accidents, of claims, of demands forrights) may be related to an object representing persons (e.g., personsassociated with investigations). Relationships between objects mayinclude one-to-one relationships, one-to-many relationship, many-to-onerelationships, many-to-many relationships, and/or other relationships.

In some embodiments, a definition of an object may be included within anontology. An ontology may include one or more objects/types of objectsrepresenting different things. An ontology may define other aspects ofobjects, such as how properties of an object may be presented and/ormodified. For example, an ontology may include a person object typeincluding a name property, and the ontology may define how the name maybe presented (e.g., first name followed by last name; last name followedby first name; first initial followed by last name). The ontology maydefine how/whether the name may be modified (e.g., based on user input,based on user account privileges). As another example, a definition of aperson object may include one or more relationship properties and theontology may define how/whether the relationship(s) may be presentedand/or modified. In some embodiments, an ontology may define whether/howproperties of an object may be created and/or removed. For example, anontology may define whether a user may add or remove one or moreproperties of the person object type. The definitions/ontologies may becreated based on user input. The definitions/ontologies may be modified(e.g., based on user input, based on system changes).

The association engine 116 may be configured to associate one or moreobjects with information stored in one or more datasets. Associatingobject(s) with information stored in dataset(s) may includeconnecting/linking the object(s) with the information stored in thedataset(s). The information to be associated with object(s) may bedetermined based at least in part on the definition(s) of the object(s).For example, a definition of an object may specify/identify particularcolumns and/or rows of a dataset including relevant values of propertiesof the object, and the association engine 116 may associate the objectwith the values in the specified/identified portions of the dataset.Individual portions of the dataset may include individual values (e.g.,numbers, strings) for individual properties of the object. In someembodiments, an object may be associated with multiple values of aproperty (e.g., a person object may be associated with multiple phonenumbers). In some embodiments, an object may be associated with multiplevalues of a property via links between objects. For example, a phonenumber object may be associated with multiple values of phone numbersincluded in a dataset and the phone number object may be linked to aperson object to associate the person object with multiple values of thephone numbers. In some embodiments, one or more associations betweeninformation and objects may be secured such that usage (e.g., viewing,modifying) of the objects/particular properties of the object may berestricted based on security/authorization level of the users/systems.

In some embodiments, the association engine 116 may be configured tochange the association of an object with information stored indataset(s) based on changes to the definition/ontology of the object.For example, a definition/ontology of an object may be changed so thatthe specified/identified portion of the dataset for a property of theobject is changed (e.g., changed to a different column, a different row,and/or a different range). Responsive to the change in thespecification/identification of the portion(s) of the dataset, theassociation engine 116 may update the association of the object with thechanged/new information.

In some embodiments, an object may be backed by a single row/column in adataset with a single primary key column/row. In such a case, the objectmay be uniquely identified by a dataset resource identifier, a branch, aprimary key column/row name, and a primary key value. In someembodiments, an object may be backed by a single row/column in a datasetwith a multi-column/row primary key. In such a case, one or moretransforms may be used to reduce the backing to the single primary keycolumn/row case. In some embodiments, an object may be backed byrows/columns from a single dataset or multiple datasets.

The cache engine 118 may be configured to store the object(s) in one ormore caches such that the information associated with the object(s) isalso stored in the cache(s). In some embodiments, the cache engine 118may store information associated with object(s) in the cache(s) based onreview of one or more commit logs. Commit logs may provide informationrelating to one or more changes to the information associated withobject(s). Storing the information associated with an object in thecache may enable users to perform one or more operations on theobject/information associated with the object. Storing the informationassociated with an object in the cache may enable users to performobject-oriented operations on the object/information associated with theobject. For example, storing the information associated with an objectin the cache may enable users to perform searching, loading, andmodifying operations on the object/information associated with theobject. The operations may be performed within the cache. The storedinformation may be used to perform operations without loading theentirety of datasets and parsing the datasets for operations. The storedinformation may be used to perform operations that are not supported bya database.

In some embodiments, one or more objects may be stored in an objectstore. An object store (e.g., via an object store server) may manage oneor more objects stored in the cache(s) by the cache engine 118. In someembodiments, the object store may include one or more caches in whichthe object(s) are stored. Storing objects in an object store may provideusers with ready access to objects that have been previously stored in acache. In some embodiments, the objects may be modified within the cacheand the modified objects may be stored in the object store. For example,based on user and/or system inputs, one or more properties/values ofproperties of an object may be modified within the cache. Themodifications of the object/properties of the object may be propagatedto the object store so that the users are provided with latestmodifications to the object. In some embodiments, the object store mayuse version control to keep track of different versions/modifications ofobjects.

In some embodiments, the information in the dataset(s) may be changed.The cache engine 118 may update the information stored in the cachebased on changes to the information in the dataset(s). For example, theinformation in the dataset(s) may include values for a name of a person.A person object (and the information associated with the person object)for the person may have been stored in a cache. After the person objecthas been stored in the cache, the values for the name of the person maybe changed within the dataset(s) (e.g., a user correcting a misspellingof the person's name; the name being updated based on a name change).The values of the person's name in the cache may be updated based on thechanges to the name in the dataset(s) so that the cache includes themodified name. Thus, the information stored in the cache may besynchronized to the changes in the underlying information in thedatasets.

In some embodiments, one or more changes to a definition of an object(e.g., within the ontology) may be identified (e.g., by the definitionengine 114). Changes to the definition of the object may changeinformation to which the object is associated. Changes to information towhich an object is associated may include: (1) changes in the propertiesspecified/identified for the object (e.g., addition of a new property,removal of an existing property, change in an existing property), (2)changes in portions of the datasets from which values of the propertiesare obtained/derived (e.g., changes in which rows/columns are associatedwith the object), (3) changes in relationships of an object, and/orother changes to the object. The cache engine 118 may update theobject/information associated with the object in the cache based on thechanges to the definition of the object.

In some embodiments, other changes relating to objects/informationassociated with the object may be detected. For example, changes toother portions of an ontology (e.g., defining how/whether properties ofobjects may be presented and/or modified) may be detected and propagatedto other parts/functionalities of the system 102. In some embodiments,one or more versions controls may be used to keep track of differentversions/modifications of definitions/ontologies.

In some embodiments, information about modifications to one or moreobjects may be stored in one or more commit logs. Modifications toobjects may include modifications to objects/information associated withobjects based on (1) changes in the underlying information (e.g.,changes in values of the dataset), (2) changes to definitions (e.g.,changes in properties of the objects, changes in where the informationfor the properties are located), (3) changes based on interactions withthe objects/information associated with the object in the cache, and/orother modifications. The information about modifications to the objectsmay include time stamps and vector clocks associated with themodifications to the objects. The information about modifications toobjects may distinguish vector clocks based on where the modificationsoriginated. For example, the vector clocks may be distinguished (e.g.,via different identifiers) based on whether the modifications originatedfrom changes in the underlying datasets (e.g., based on datatransaction) or from changes made to the object in the cache based onuser/system interaction with the object (e.g., based on cachetransaction). Time stamps and/or vector clocks may be used to determinewhen the modifications were made to the objects, when conflicts existsbetween modifications to objects, and/or to resolve conflicts betweenmodifications to the objects.

In some embodiments, it may be impractical to store a vector clock forevery object being stored in the cache. For example, in case of largedatasets/large number of objects, such storage of vector clocks may leadto storage problems. In some embodiments, instead of storing a vectorclock for every object, one vector clock may be stored per dataset, andone clock may be stored per new/modified object. Such storage of vectorclocks may allow for assumption of a default vector clock per dataset,with potential of additional vector clocks for modified objects.

In some embodiments, usage of vector clocks may be simplified by storingthe vector clocks internally when objects are stored in a cache. Avector clock may be associated with each version of an object. When anobject is modified in the cache, it may have an updated vector clock.When users make modifications to the object and the modifications aremerged into the cache, the cached object may have an incremented vectorclock associated with the modifications being made in the cache. Whenmodifications of information in the dataset(s) are synchronized into thecache, the new version of the object may have the appropriate vectorclock entry from the dataset transaction.

In some embodiments, the information about modifications to the objectsmay identify user(s)/system(s) that prompted/made the modifications. Theidentification of users/systems that prompted/made the modification maybe used as fingerprints to determine the entity that modified theobjects. In some embodiments, the information may identify securitylevel(s) of user(s)/system(s) that prompted/made the modifications. Theidentification of security levels may be used to determine the types ofmodifications and/or which modifications may take precedence over othermodifications. In some embodiments, the information may identify thepriority levels of the modifications. The identification of prioritylevels of modifications may be used to determine the order in which themodifications may be made and/or which modifications may take precedenceover other modifications.

In some embodiments, information about modifications to one or moreobjects may be stored in one or more commit logs before themodifications are made to the object(s). The modifications may be pushedto the objects in the cache after any conflicts/problems with themodifications have been resolved. The modifications to the objects maybe stored back in the dataset(s).

In some embodiments, conflicts in the modifications to the object may beidentified based on one or more commit logs. For example, while a useris modifying an object in the cache, the underlying information in thedataset(s) may be modified (e.g., by another user, by a system). Theconflict in the modifications to the object may be detected based oncomparison of vector clocks for the object.

The conflicts may be resolved based on one or more set and/orconfigurable rules. For example, conflicts may be resolved based ontiming of the modifications (e.g., first to modify wins, the last tomodify wins). Conflicts may be resolved based on where the modificationoriginated (e.g., modification based on dataset transactions wins overmodifications based on cache transactions, or vice versa). Conflicts maybe resolved based on security levels and/or priority levels ofusers/systems that prompted/made the modifications. In some embodiments,conflicts arising from modifications made by multiple users may beresolved by favoring particular users over other users or requiring oneor more of the users to resolve the conflict (e.g., by requiring user(s)to determine which modification to allow, by requiring users to reenterthe modifications). Allowing users to modify the rules by whichconflicts are resolved may enable flexible resolution strategies to beemployed for different situations. In some embodiments, the resolutionof a conflict may result in a resolved version of the object and aresolved vector clock, which may be stored as the new vector clock forthe given object.

The interface engine 120 may be configured to provide one or moreinterfaces through which requests to perform one or more operations onthe object(s) are able to be submitted. The interface(s) may includeapplication program interface(s) and/or user interface(s) through whichoperation(s) on the objects may be submitted. For example, the interfaceengine 120 may provide one or more APIs that may be used byusers/computing systems to search, load, and/or modifyobjects/information associated with the object. The object may be foundwithin the cache based on a search request (using an object search API).The object may be loaded based on a load request (using an object loadAPI). The object may be modified based on a modification request (usingan object modify API). As another example, the interface engine 120 mayprovide one or more user interfaces (e.g., web user interface) throughwhich users may enter/select commands to search, load, and/or modifyobjects/information associated with the object. Other operations onobjects/information associated with objects are contemplated.

A search request may return one or more objects that match one or moresearching criteria. Criteria for search request may include one or moreparameters relating to properties of objects, reference identifiers ofobjects, and/or other criteria. In some embodiments, a referenceidentifier for an object may include one or more of a service, instance,type, and/or locator. In some embodiments, a search request may supporta keyword filter (e.g., searching one or more fields of objects forspecified query string/value), an object type filter (e.g., limiting thesearch results to a specific set of object types), a property filter(e.g., specifying query string/value to match on one or more specificproperties for a specific object/object type and/or one or more globalproperties that multiple objects/object types may share). A searchresult may require matching on some or all of the specified criteria. Insome embodiments, the objects in the cache may enable a full-text searchand may enforce permissions/security on datasets. Individual objects maybe indexed as its own document.

A load request may load one or more objects for additional operations bythe users/systems. The load request may load up-to-date version of theobject. On a load, a unique identifier for the object may be used.

A modification request may change one or more aspects of objects in thecache/loaded objects. A modification request may include creation,removal, and/or changes in values of the properties of the objects. Amodification request may create, remove, and/or change properties of theobjects. In some embodiments, creation of new properties for an objectmay result in creation of new information in the underlying datasets.The modifications to the objects may be made in the cache. Themodifications to the objects in the cache may be propagated to theunderlying datasets.

For example, a user may use the search request to locate a given objectand load the given object for additional operations. The user may viewparticular aspects of the given object (information associated with thegiven object). Views of the given object may include views ofinformation associated with objects related to the given object and/oridentification of objects related to the given object. The users maymodify the given object (e.g., change/remove existing properties of theobject, create new properties to the object, change/remove existingrelationships of the object, create new relationships of the object).The changes made by the user may be stored within the cache (e.g., inobject store) and/or may be propagated to the datasets (e.g., inrelational database(s)) from which the information associated with thegiven object is obtained.

FIG. 2 illustrates an example environment 200 for providing an objectplatform for datasets, in accordance with various embodiments. Theexample environment 200 may include a database 210 and an object cache230. In some embodiments, the object cache 230 may be stored in anobject store. The database 210 may include one or more databases. Thedatabase 210 may include one or more datasets including a string 212, avalue 214, and/or other datasets/information. The string 212 and thevalue 214 may be organized into tables, columns, rows, and/or otherorganizational groupings. The string 214 and the value 214 may belinked/referenced via use of keys. The database may include a commit log220. In some embodiments, the commit log 220 may be stored in otherlocations.

A definition for an object may specify/identify the string 212 and thevalue 214 as the portions of a dataset in which values of properties ofthe object are located. Based on the definition, the string 212 and thevalue 214 may be associated with the object. The object may be stored inthe object cache 230 as object 240. Storing the object 240 in the objectcache 230 may include storing the string 212 and the value 214 as string242 and value 244, respectively, in the object cache 230. In someembodiments, the object 240, the string 242, and the value 244 may bestored in the object cache 230 based on a review of the commit log 220associated with the object. In some embodiments, the storage of theobject 240/the string 242, the value 244 in the object cache 230 may beimplemented by one or more object store servers. Storing the object240/the string 242, the value 244 in the object cache 230 may be part ofa cache warming process. The object 240 may be queried, loaded, and/ormodified via one or more interfaces (e.g., APIs, user interfaces).Changes to the string 212 and/or the value 214 in the database 210 maybe propagated to the string 242 and/or the value 244 in the object cache230. Changes to the string 242 and/or the value 244 in the object cache230 may be propagated to the string 212 and/or the value 214 in thedatabase 210. Information relating to the changes to the string 212, 242and the value 214, 244 may be stored in the commit log 220.

FIG. 3 illustrates an example operation flow 300 for using an objectplatform for datasets, in accordance with various embodiments. Theoperation flow 300 may include operations on a database 310 (including astring 312, a value 314, a commit log 320) and an object cache 330(including an object 340, a string 342, a value 344). In someembodiments, the database 310 (including the string 312, the value 314,the commit log 320) may be configured to implement some, or all, of thefunctionalities of the database 210 (including the string 212, the value214, the commit log 220) as described above. In some embodiments, theobject cache 330 (including the object 340, the string 342, the value344) may be configured to implement some, or all, of the functionalitiesof the object cache 230 (including the object 240, the string 242, thevalue 244) as described above.

One or more operations may be performed on the object 340 (e.g., afterthe object 340 has been queried and loaded). For example, as shown inFIG. 3, a modification operation 352 may be performed on the object 340(e.g., via an object store server) to modify the string 342, the value344, and/or other aspects of the object 340. The modifications to theobject 340 may be pushed 354 to the commit log 320. In some embodiments,the commit log 320 may be used to detect and/or resolve conflictsbetween modifications to the object 340. The modifications to the object340 may be stored 356A, 356B in the object cache 330 and in the database310.

FIG. 4 illustrates a flowchart of an example method 400, according tovarious embodiments of the present disclosure. The method 400 may beimplemented in various environments including, for example, theenvironment 100 of FIG. 1. The operations of method 400 presented beloware intended to be illustrative. Depending on the implementation, theexample method 400 may include additional, fewer, or alternative stepsperformed in various orders or in parallel. The example method 400 maybe implemented in various computing systems or devices including one ormore processors.

At block 402, a definition of an object may be obtained. At block 404,the object may be associated with information stored in one or moredatasets. The information may be determined based at least in part onthe definition of the object. At block 406, the object may be stored ina cache such that the information associated with the object is alsostored in the cache. At block 408, one or more interfaces through whichrequests to perform one or more operations object are able to besubmitted may be provided.

Hardware Implementation

The techniques described herein are implemented by one or morespecial-purpose computing devices. The special-purpose computing devicesmay be hard-wired to perform the techniques, or may include circuitry ordigital electronic devices such as one or more application-specificintegrated circuits (ASICs) or field programmable gate arrays (FPGAs)that are persistently programmed to perform the techniques, or mayinclude one or more hardware processors programmed to perform thetechniques pursuant to program instructions in firmware, memory, otherstorage, or a combination. Such special-purpose computing devices mayalso combine custom hard-wired logic, ASICs, or FPGAs with customprogramming to accomplish the techniques. The special-purpose computingdevices may be desktop computer systems, server computer systems,portable computer systems, handheld devices, networking devices or anyother device or combination of devices that incorporate hard-wiredand/or program logic to implement the techniques.

Computing device(s) are generally controlled and coordinated byoperating system software, such as iOS, Android, Chrome OS, Windows XP,Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix,Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatibleoperating systems. In other embodiments, the computing device may becontrolled by a proprietary operating system. Conventional operatingsystems control and schedule computer processes for execution, performmemory management, provide file system, networking, I/O services, andprovide a user interface functionality, such as a graphical userinterface (“GUI”), among other things.

FIG. 5 is a block diagram that illustrates a computer system 500 uponwhich any of the embodiments described herein may be implemented. Thecomputer system 500 includes a bus 502 or other communication mechanismfor communicating information, one or more hardware processors 504coupled with bus 502 for processing information. Hardware processor(s)504 may be, for example, one or more general purpose microprocessors.

The computer system 500 also includes a main memory 506, such as arandom access memory (RAM), cache and/or other dynamic storage devices,coupled to bus 502 for storing information and instructions to beexecuted by processor 504. Main memory 506 also may be used for storingtemporary variables or other intermediate information during executionof instructions to be executed by processor 504. Such instructions, whenstored in storage media accessible to processor 504, render computersystem 500 into a special-purpose machine that is customized to performthe operations specified in the instructions.

The computer system 500 further includes a read only memory (ROM) 508 orother static storage device coupled to bus 502 for storing staticinformation and instructions for processor 504. A storage device 510,such as a magnetic disk, optical disk, or USB thumb drive (Flash drive),etc., is provided and coupled to bus 502 for storing information andinstructions.

The computer system 500 may be coupled via bus 502 to a display 512,such as a cathode ray tube (CRT) or LCD display (or touch screen), fordisplaying information to a computer user. An input device 514,including alphanumeric and other keys, is coupled to bus 502 forcommunicating information and command selections to processor 504.Another type of user input device is cursor control 516, such as amouse, a trackball, or cursor direction keys for communicating directioninformation and command selections to processor 504 and for controllingcursor movement on display 512. This input device typically has twodegrees of freedom in two axes, a first axis (e.g., x) and a second axis(e.g., y), that allows the device to specify positions in a plane. Insome embodiments, the same direction information and command selectionsas cursor control may be implemented via receiving touches on a touchscreen without a cursor.

The computing system 500 may include a user interface module toimplement a GUI that may be stored in a mass storage device asexecutable software codes that are executed by the computing device(s).This and other modules may include, by way of example, components, suchas software components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables.

In general, the word “module,” as used herein, refers to logic embodiedin hardware or firmware, or to a collection of software instructions,possibly having entry and exit points, written in a programminglanguage, such as, for example, Java, C or C++. A software module may becompiled and linked into an executable program, installed in a dynamiclink library, or may be written in an interpreted programming languagesuch as, for example, BASIC, Perl, or Python. It will be appreciatedthat software modules may be callable from other modules or fromthemselves, and/or may be invoked in response to detected events orinterrupts. Software modules configured for execution on computingdevices may be provided on a computer readable medium, such as a compactdisc, digital video disc, flash drive, magnetic disc, or any othertangible medium, or as a digital download (and may be originally storedin a compressed or installable format that requires installation,decompression or decryption prior to execution). Such software code maybe stored, partially or fully, on a memory device of the executingcomputing device, for execution by the computing device. Softwareinstructions may be embedded in firmware, such as an EPROM. It will befurther appreciated that hardware modules may be comprised of connectedlogic units, such as gates and flip-flops, and/or may be comprised ofprogrammable units, such as programmable gate arrays or processors. Themodules or computing device functionality described herein arepreferably implemented as software modules, but may be represented inhardware or firmware. Generally, the modules described herein refer tological modules that may be combined with other modules or divided intosub-modules despite their physical organization or storage.

The computer system 500 may implement the techniques described hereinusing customized hard-wired logic, one or more ASICs or FPGAs, firmwareand/or program logic which in combination with the computer systemcauses or programs computer system 500 to be a special-purpose machine.According to one embodiment, the techniques herein are performed bycomputer system 500 in response to processor(s) 504 executing one ormore sequences of one or more instructions contained in main memory 506.Such instructions may be read into main memory 506 from another storagemedium, such as storage device 510. Execution of the sequences ofinstructions contained in main memory 506 causes processor(s) 504 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “non-transitory media,” and similar terms, as used hereinrefers to any media that store data and/or instructions that cause amachine to operate in a specific fashion. Such non-transitory media maycomprise non-volatile media and/or volatile media. Non-volatile mediaincludes, for example, optical or magnetic disks, such as storage device510. Volatile media includes dynamic memory, such as main memory 506.Common forms of non-transitory media include, for example, a floppydisk, a flexible disk, hard disk, solid state drive, magnetic tape, orany other magnetic data storage medium, a CD-ROM, any other optical datastorage medium, any physical medium with patterns of holes, a RAM, aPROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge, and networked versions of the same.

Non-transitory media is distinct from but may be used in conjunctionwith transmission media. Transmission media participates in transferringinformation between non-transitory media. For example, transmissionmedia includes coaxial cables, copper wire and fiber optics, includingthe wires that comprise bus 502. Transmission media can also take theform of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 504 for execution. For example,the instructions may initially be carried on a magnetic disk or solidstate drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 500 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 502. Bus 502 carries the data tomain memory 506, from which processor 504 retrieves and executes theinstructions. The instructions received by main memory 506 may retrievesand executes the instructions. The instructions received by main memory506 may optionally be stored on storage device 510 either before orafter execution by processor 504.

The computer system 500 also includes a communication interface 518coupled to bus 502. Communication interface 518 provides a two-way datacommunication coupling to one or more network links that are connectedto one or more local networks. For example, communication interface 518may be an integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example,communication interface 518 may be a local area network (LAN) card toprovide a data communication connection to a compatible LAN (or WANcomponent to communicated with a WAN). Wireless links may also beimplemented. In any such implementation, communication interface 518sends and receives electrical, electromagnetic or optical signals thatcarry digital data streams representing various types of information.

A network link typically provides data communication through one or morenetworks to other data devices. For example, a network link may providea connection through local network to a host computer or to dataequipment operated by an Internet Service Provider (ISP). The ISP inturn provides data communication services through the world wide packetdata communication network now commonly referred to as the “Internet”.Local network and Internet both use electrical, electromagnetic oroptical signals that carry digital data streams. The signals through thevarious networks and the signals on network link and throughcommunication interface 518, which carry the digital data to and fromcomputer system 500, are example forms of transmission media.

The computer system 500 can send messages and receive data, includingprogram code, through the network(s), network link and communicationinterface 518. In the Internet example, a server might transmit arequested code for an application program through the Internet, the ISP,the local network and the communication interface 518.

The received code may be executed by processor 504 as it is received,and/or stored in storage device 510, or other non-volatile storage forlater execution.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computer systems or computerprocessors comprising computer hardware. The processes and algorithmsmay be implemented partially or wholly in application-specificcircuitry.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some embodiments. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example embodiments.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure. The foregoing description details certainembodiments of the invention. It will be appreciated, however, that nomatter how detailed the foregoing appears in text, the invention can bepracticed in many ways. As is also stated above, it should be noted thatthe use of particular terminology when describing certain features oraspects of the invention should not be taken to imply that theterminology is being re-defined herein to be restricted to including anyspecific characteristics of the features or aspects of the inventionwith which that terminology is associated. The scope of the inventionshould therefore be construed in accordance with the appended claims andany equivalents thereof.

Engines, Components, and Logic

Certain embodiments are described herein as including logic or a numberof components, engines, or mechanisms. Engines may constitute eithersoftware engines (e.g., code embodied on a machine-readable medium) orhardware engines. A “hardware engine” is a tangible unit capable ofperforming certain operations and may be configured or arranged in acertain physical manner. In various example embodiments, one or morecomputer systems (e.g., a standalone computer system, a client computersystem, or a server computer system) or one or more hardware engines ofa computer system (e.g., a processor or a group of processors) may beconfigured by software (e.g., an application or application portion) asa hardware engine that operates to perform certain operations asdescribed herein.

In some embodiments, a hardware engine may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware engine may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware engine may be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware engine may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardware enginemay include software executed by a general-purpose processor or otherprogrammable processor. Once configured by such software, hardwareengines become specific machines (or specific components of a machine)uniquely tailored to perform the configured functions and are no longergeneral-purpose processors. It will be appreciated that the decision toimplement a hardware engine mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) may be driven by cost and time considerations.

Accordingly, the phrase “hardware engine” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented engine” refers to a hardware engine. Consideringembodiments in which hardware engines are temporarily configured (e.g.,programmed), each of the hardware engines need not be configured orinstantiated at any one instance in time. For example, where a hardwareengine comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware engines) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware engine at one instance oftime and to constitute a different hardware engine at a differentinstance of time.

Hardware engines can provide information to, and receive informationfrom, other hardware engines. Accordingly, the described hardwareengines may be regarded as being communicatively coupled. Where multiplehardware engines exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware engines. In embodiments inwhich multiple hardware engines are configured or instantiated atdifferent times, communications between such hardware engines may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware engines have access.For example, one hardware engine may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware engine may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware engines may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented enginesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented engine” refers to ahardware engine implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented engines. Moreover, the one or more processors mayalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example embodiments, the processorsor processor-implemented engines may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented engines may be distributed across a number ofgeographic locations.

Language

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the subject matter has been described withreference to specific example embodiments, various modifications andchanges may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the subject matter may be referred to herein, individually orcollectively, by the term “invention” merely for convenience and withoutintending to voluntarily limit the scope of this application to anysingle disclosure or concept if more than one is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

It will be appreciated that an “engine,” “system,” “data store,” and/or“database” may comprise software, hardware, firmware, and/or circuitry.In one example, one or more software programs comprising instructionscapable of being executable by a processor may perform one or more ofthe functions of the engines, data stores, databases, or systemsdescribed herein. In another example, circuitry may perform the same orsimilar functions. Alternative embodiments may comprise more, less, orfunctionally equivalent engines, systems, data stores, or databases, andstill be within the scope of present embodiments. For example, thefunctionality of the various systems, engines, data stores, and/ordatabases may be combined or divided differently.

“Open source” software is defined herein to be source code that allowsdistribution as source code as well as compiled form, with awell-publicized and indexed means of obtaining the source, optionallywith a license that allows modifications and derived works.

The data stores described herein may be any suitable structure (e.g., anactive database, a relational database, a self-referential database, atable, a matrix, an array, a flat file, a documented-oriented storagesystem, a non-relational No-SQL system, and the like), and may becloud-based or otherwise.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, engines, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Although the invention has been described in detail for the purpose ofillustration based on what is currently considered to be the mostpractical and preferred implementations, it is to be understood thatsuch detail is solely for that purpose and that the invention is notlimited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present invention contemplates that, to theextent possible, one or more features of any embodiment can be combinedwith one or more features of any other embodiment.

1. A system comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe system to perform: obtaining a definition of an object includedwithin an ontology; associating the object with information stored inone or more datasets of a relational database, the information beingdetermined based at least in part on the definition of the object;storing the object in a cache such that the information associated withthe object is also stored in the cache; and providing one or moreobject-oriented interfaces through which requests to perform one or moreobject-oriented operations on the object are able to be submitted. 2.The system of claim 1, wherein the object-oriented operations includesearching for the object, loading the object, or modifying the object.3. (canceled)
 4. The system of claim 2, wherein the object is modifiedwithin the cache.
 5. The system of claim 4, wherein the modified objectis stored in an object store.
 6. The system of claim 1, wherein theinstructions further cause the system to perform: identifying a changeto the definition of the object; and updating the object in the cachebased on the change to the definition of the object.
 7. The system ofclaim 2, wherein information about modifications to the object arestored in a commit log, the information including time stamps and vectorclocks associated with the modifications to the object.
 8. The system ofclaim 7, wherein the instructions further cause the system to perform:identifying conflicts in the modifications to the object based on thecommit log; and resolving the conflicts.
 9. A method implemented by acomputing system including one or more processors and storage mediastoring machine-readable instructions, wherein the method is performedusing the one or more processors, the method comprising: obtaining adefinition of an object included within an ontology; associating theobject with information stored in one or more datasets of a relationaldatabase, the information being determined based at least in part on thedefinition of the object; storing the object in a cache such that theinformation associated with the object is also stored in the cache; andproviding one or more object-oriented interfaces through which requeststo perform one or more object-oriented operations on the object are ableto be submitted.
 10. The method of claim 9, wherein the object-orientedoperations include searching for the object, loading the object, ormodifying the object.
 11. (canceled)
 12. The method of claim 10, whereinthe object is modified within the cache.
 13. The method of claim 12,wherein the modified object is stored in an object store.
 14. The methodof claim 9, further comprising: identifying a change to the definitionof the object; and updating the object in the cache based on the changeto the definition of the object.
 15. The method of claim 10, whereininformation about modifications to the object are stored in a commitlog, the information including time stamps and vector clocks associatedwith the modifications to the object.
 16. The method of claim 15,further comprising: identifying conflicts in the modifications to theobject based on the commit log; and resolving the conflicts.
 17. Anon-transitory computer readable medium comprising instructions that,when executed, cause one or more processors to perform: obtaining adefinition of an object included within an ontology; associating theobject with information stored in one or more datasets of a relationaldatabase, the information being determined based at least in part on thedefinition of the object; storing the object in a cache such that theinformation associated with the object is also stored in the cache; andproviding one or more object-oriented interfaces through which requeststo perform one or more object-oriented operations on the object are ableto be submitted.
 18. The non-transitory computer readable medium ofclaim 17, wherein the object-oriented operations include searching forthe object, loading the object, or modifying the object.
 19. Thenon-transitory computer readable medium of claim 18, wherein themodified object is stored in an object store.
 20. The non-transitorycomputer readable medium of claim 18, wherein information aboutmodifications to the object are stored in a commit log, the informationincluding time stamps and vector clocks associated with themodifications to the object.